Multicasting traffic using multi-connectivity

ABSTRACT

Certain aspects of the present disclosure relate to methods and apparatus for wireless communication, and more particularly, to methods and apparatus for multicasting traffic using multi-connectivity. A wireless network can send a downlink (DL) packet, which follows one path from a core network entity to a user equipment (UE) under current standards, to multiple base stations (BSs) and from each of the base stations to a UE. The UE receives the DL packet from whichever BS first delivers the DL packet, and then the UE sends a report reporting receipt of the DL packet back to all of the BSs. BSs that receive a report indicating the UE received the packet can drop the packet, even if they have not yet successfully delivered the packet. The same procedure can be used for an UL packet, which can be sent from a UE to multiple BSs, and from the BSs to a core network entity.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application for patent claims priority to U.S. ProvisionalApplication No. 62/039,227, filed Aug. 19, 2014, which is assigned tothe assignee of the present application and hereby expresslyincorporated by reference herein in its entirety.

BACKGROUND

1. Field of the Disclosure

The present disclosure relates generally to wireless communication, andmore particularly, to methods and apparatus for multicasting trafficusing multi-connectivity.

2. Description of Related Art

Wireless communication systems are being developed with the goal ofenabling new services and devices, which will offer new userexperiences. One approach to achieve this is to leverage multipleexisting radio access technologies (RATs), for example, using acombination of features from wireless wide area networks (e.g., 3G andLTE) and wireless local area networks (e.g., based on WiFi andmillimeter wave (mmW)). This approach may help speed development andtake advantage of different benefits provided by the different RATs.

One challenge with a system that utilizes multiple RATs is how tooptimally route data between a core network and a user, given thedifferent paths offered by the different RATs.

BRIEF SUMMARY

Certain aspects of the present disclosure provide a method of reportinga status for a data flow. The method generally includes determining adata flow is being received from a plurality of connections andreporting, on more than one connection of the plurality of connections,a status for a packet received on the data flow.

Certain aspects of the present disclosure provide a method oftransmitting a data flow. The method generally includes determining adata flow is to be transmitted on a plurality of connections, whereinthe data flow is sent according to layers in a protocol stack below alayer determined based on a selection of a packet split at anaggregation point, and forwarding data for the data flow on theplurality of connections.

Certain aspects of the present disclosure provide an apparatus forreporting a status for a data flow. The apparatus generally includesmeans for determining a data flow is being received from a plurality ofconnections and means for reporting, on more than one connection of theplurality of connections, a status for a packet received on the dataflow.

Certain aspects of the present disclosure provide an apparatus fortransmitting a data flow. The apparatus generally includes means fordetermining a data flow is to be transmitted on a plurality ofconnections, wherein the data flow is sent according to layers in aprotocol stack below a layer determined based on a selection of a packetsplit at an aggregation point, and means for forwarding at least onedata packet for the data flow on two or more connections of theplurality of connections.

Aspects also provide various apparatus, systems, computer programproducts, and processing systems for performing the operations describedabove.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example multi-RAT system in which aspects of thepresent disclosure may be utilized.

FIGS. 2A and 2B illustrate example protocol layers for control plane anduser plane routing, in accordance with certain aspects of the presentdisclosure.

FIG. 3 illustrates an example multi-connectivity protocol stack, inaccordance with aspects of the present disclosure.

FIG. 4 illustrates example offload configuration, in accordance withaspects of the present disclosure.

FIG. 5 illustrates example user plane (U-plane) splittingconfigurations, in accordance with aspects of the present disclosure.

FIG. 6 illustrates example control plane (C-plane) logical architectureoptions, in accordance with aspects of the present disclosure.

FIG. 7 illustrates example control plane (C-plane) NAS logicalarchitecture options, in accordance with aspects of the presentdisclosure.

FIG. 8 illustrates an example call flow diagram of a UE, a master eNodeB(MeNB), and a secondary eNodeB (SeNB), in accordance with aspects of thepresent disclosure.

FIGS. 9A and 9B illustrate exemplary exchanges of messages usingmulti-connectivity, according to aspects of the present disclosure.

FIGS. 10A, 10B, 10C, and 10D illustrate exemplary exchanges of messagesusing multi-connectivity, according to aspects of the presentdisclosure.

FIG. 11 sets forth example operations that may be performed by a userequipment (UE), according to aspects of the present disclosure.

FIG. 12 sets forth example operations that may be performed by an eNodeB(eNB), according to aspects of the present disclosure.

FIG. 13 illustrates a block diagram of an example user equipment, inaccordance with aspects of the present disclosure.

FIG. 14 illustrates a block diagram of an example base station, inaccordance with aspects of the present disclosure.

DETAILED DESCRIPTION

Aspects of the present disclosure provide techniques that may be used toroute data between a core network and a user equipment (UE) connectedvia multiple radio access technologies (RATs). According to certainaspects, a downlink (DL) packet, which follows one path from a corenetwork entity to a user equipment (UE) under current standards (e.g.,Rel-12), is sent from the core network to multiple base stations (e.g.,eNodeBs and access points) and from each of the base stations to a UE.The UE receives the DL packet from whichever base station (BS) firstdelivers the DL packet, and then the UE sends a report (e.g., an ACK)reporting receipt of the DL packet back to all of the BSs. BSs thatreceive a report indicating the UE received the packet can drop thepacket, even if the BSs have not yet successfully delivered the packet.According to certain aspects of the present disclosure, an uplink (UL)packet, which follows one path from a UE to a core network entity undercurrent standards (e.g., Rel-12), is sent by the UE to multiple BSs(e.g., eNodeBs and access points) and from the base stations to a corenetwork entity. The core network entity receives the UL packet fromwhichever base station (BS) first delivers the UL packet, and then thecore network entity sends a report (e.g., an ACK) reporting receipt ofthe UL packet back to all of the BSs. BSs that receive a reportindicating the UE received the packet can drop the packet, even if theBSs have not yet successfully delivered the packet.

Aspects of the present disclosure may be applied to a wide variety ofdifferent types of mobile devices communicating via a wide variety ofdifferent RATs. Different terminology may be used to refer to mobiledevices. For example, in some cases depending on the RAT(s) supportedthereby, a mobile device may be referred to as a wireless device, userterminal (UT), access terminal (AT), user equipment (UE), station,mobile station, wireless station, wireless node, or the like. Similarly,different terminology may be used to refer to a base station thatprovides services to a mobile device, such as access to a core network.For example, in some cases depending on the RAT(s) supported thereby, abase station may be referred to as an access point (AP), a node B, anenhanced Node B (eNodeB), or simply an eNB.

In certain examples that follow, a mobile device is referred to as a UEand base stations are referred to as eNBs. Such references are not meantto limit aspects of the present disclosure to any particular RAT orRATs, but are merely to help describe illustrative examples meant tofacilitate understanding.

The detailed description set forth below in connection with the appendeddrawings is intended as a description of various configurations and isnot intended to represent the only configurations in which the conceptsdescribed herein may be practiced. The detailed description includesspecific details for the purpose of providing a thorough understandingof various concepts. However, it will be apparent to those skilled inthe art that these concepts may be practiced without these specificdetails. In some instances, well-known structures and components areshown in block diagram form in order to avoid obscuring such concepts.

Several aspects of telecommunication systems will now be presented withreference to various apparatus and methods. These apparatus and methodswill be described in the following detailed description and illustratedin the accompanying drawings by various blocks, modules, components,circuits, steps, processes, algorithms, etc. (collectively referred toas “elements”). These elements may be implemented using hardware,software, or combinations thereof. Whether such elements are implementedas hardware or software depends upon the particular application anddesign constraints imposed on the overall system.

By way of example, an element, or any portion of an element, or anycombination of elements may be implemented with a “processing system”that includes one or more processors. Examples of processors includemicroprocessors, microcontrollers, digital signal processors (DSPs),field programmable gate arrays (FPGAs), programmable logic devices(PLDs), state machines, gated logic, discrete hardware circuits, andother suitable hardware configured to perform the various functionalitydescribed throughout this disclosure. One or more processors in theprocessing system may execute software. Software shall be construedbroadly to mean instructions, instruction sets, code, code segments,program code, programs, subprograms, software modules, applications,software applications, software packages, firmware, routines,subroutines, objects, executables, threads of execution, procedures,functions, etc., whether referred to as software/firmware, middleware,microcode, hardware description language, or otherwise.

Accordingly, in one or more exemplary embodiments, the functionsdescribed may be implemented in hardware, software, or combinationsthereof. If implemented in software, the functions may be stored on orencoded as one or more instructions or code on a computer-readablemedium. Computer-readable media includes computer storage media. Storagemedia may be any available media that can be accessed by a computer. Byway of example, and not limitation, such computer-readable media cancomprise RAM, ROM, EEPROM, PCM (phase change memory), flash memory,CD-ROM or other optical disk storage, magnetic disk storage or othermagnetic storage devices, or any other medium that can be used to carryor store desired program code in the form of instructions or datastructures and that can be accessed by a computer. Disk and disc, asused herein, includes compact disc (CD), laser disc, optical disc,digital versatile disc (DVD), floppy disk and Blu-ray disc where disksusually reproduce data magnetically, while discs reproduce dataoptically with lasers. Combinations of the above should also be includedwithin the scope of computer-readable media.

An Example Wireless Environment

FIG. 1 illustrates an example wireless environment 100, in which aspectsof the present disclosure may be utilized to manage data flows between acore network and a wireless device, such as UE 110.

As illustrated, UE 110 may be capable of communicating with multiplebase stations, such as a master eNodeB (MeNB) 120 and a secondary eNodeB(SeNB) 130. MeNB 120 and SeNB 130 may communicate via the same RAT ordifferent RATs. For example, MeNB 120 may communicate via a wirelesswide area network (WWAN) protocol (e.g. LTE) while SeNB 130 maycommunicate via a wireless local area network (WLAN) protocol (e.g.,WiFi).

As used herein, the term MeNB generally refers to an eNB that terminatesan S1-MME (Mobility Management Entity) control plane for the UE, whilethe term SeNB generally refers to an eNB serving the UE that is not theMeNB. An S1 connection may be used by the MeNB or SeNB to communicatewith the core network (CN), for example via a CN gateway (GW) 140. Forexample, the S1 interface may include an S1-U interface, which servesthe data plane between the MeNB or SeNB and the CN GW, and an S1-MME,which serves the control plane.

In certain aspects, the MeNB may be connected to one or more SeNBs toserve a UE via multi-connectivity. The MeNB and SeNB may communicatewith one another via a backhaul connection 150 (e.g., an X2 connection).The backhaul connection need not be direct but may be routed through oneor more intermediate nodes (e.g., an MME, an interworking gatewayfunction, or a router). The number of SeNBs may be limited, depending onthe capabilities of the UE. The MeNB may coordinate mobility anduser-plane (U-plane) split procedures within the corresponding operatornetwork. The MeNB may be considered as “access agnostic,” meaning it maysupport any type of RAT both to serve the UE and also for managing theUE configuration of a U-plane split with one or more SeNBs. For example,an MeNB may utilize a common U-plane anchored in the operator's corenetwork (CN) in order to enable procedures to manage the U-plane splitvia multiple RATs, as described herein.

The SeNB may be utilized as a source of supplemental capacity for theMeNB and may also use a different RAT (from the RAT of the MeNB) toserve the UE. According to aspects of the present disclosure, an SeNB islimited to serving a UE and in most cases may not be used to control theUE configuration of the U-plane split. Having the SeNB as a supplementalcapacity for the MeNB may provide an opportunistic and energy efficientoperation, which may be initiated by the UE's user or the networkoperator.

The SeNB may be loosely or tightly coupled with the MeNB, depending onbackhaul bandwidth capabilities and latency requirements. For example,an SeNB that is considered tightly coupled with an MeNB may have theSeNB's connection to the UE substantially managed by the MeNB. On theother hand, an SeNB that is considered loosely coupled with an MeNB mayleave the SeNB's connection to the UE under the control of the SeNBsubject to, for example, general requirements such as Quality of Service(QoS) from the MeNB. For example, an SeNB with a high-capacity andlow-latency backhaul link to an MeNB may be tightly coupled with theoperations of the MeNB. The SeNB may be used as a supplemental downlink(SDL) or as an additional cell for both uplink (UL) and DL. In somecases, the SeNB may be used to help achieve supplemental mobilityrobustness of the MeNB, for example, for mission critical applications.For example, the SeNB may provide a redundant path for delivery ofcritical information and may also provide a fast failover (to the SeNB)in the event the MeNB experiences a radio link failure (RLF).

Multi-connectivity (MC) generally refers to a mode of operation whereina UE is connected (e.g., radio resource control (RRC) connected) to anMeNB and at least one SeNB, as illustrated in FIG. 1. FIG. 1 shows aspecific example of MC, with two different eNBs, that may be referred toas dual connectivity (DC). In MC, a group of serving cells associatedwith the MeNB, including a primary cell (PCell) and optionally one ormore secondary cells (SCells), may be referred to as a master cell group(MCG). Similarly, a group of serving cells associated with the SeNB maybe referred to as a secondary cell group (SCG).

Certain aspects of the present disclosure present MC procedures whichinclude procedures to change (add to an SCG, remove from an SCG, ormodify the configuration of) one or more cells of an SeNB, whilemaintaining a current MeNB. As will be described in greater detailbelow, MC procedures may include various options for offloading datacommunications using MC, for example, at the packet level, bearer level,or access packet network (APN) level.

MC procedures may also include handover procedures to change the MeNB,e.g., by transferring the functionality of the MeNB for a UE's MCconfiguration to another eNB, as well as additional aggregationprocedures. The aggregation procedures may include procedures to change(add, remove, or modify) a set of one or more secondary componentcarriers (SCC) of the MeNB and/or an SeNB. In some cases, aggregationmay imply a primary component carrier (PCC) controlling one or moresecondary component carrier (SCCs) with a common media access control(MAC) layer.

The present disclosure provides various options for aggregation andU-plane splitting, such as aggregation within a same node, (e.g.,carrier aggregation) and U-plane splitting across nodes via the radioaccess network (RAN). For example, for multi-connectivity, a data flowmay be split on a per-packet basis or split on a per-bearer basis (e.g.,split over the X2 interface instead of the S1 interface).

In some cases, the U-plane may also be split across nodes via the CN,for example, via a bearer-split using multi-connectivity. That is, a CNsending data via multiple bearers e.g., Bearer A and Bearer B in FIG. 1,to a UE may use multi-connectivity to assign one bearer to an MeNB and asecond bearer to an SeNB, and send data packets to the MeNB and SeNBbased on which bearer each packet is traversing.

Another option for aggregation and U-plane splitting is non-seamlessoffload, which may include offloading to another operator (if allowed),for example, if session continuity is not necessary. This may beconsidered equivalent to per-packet splitting if multi-path transmissioncontrol protocol (MP-TCP) is available, otherwise the split may occur atthe Internet protocol (IP) flow level. Another option is multicasting(e.g., bi-casting) traffic wherein, for example, each packet is servedby both the MeNB and SeNB for greater reliability.

Aspects of the present disclosure describe several possibleconsiderations for making aggregation and U-plane split decisions. Insome cases, aggregation in a node may utilize a common MAC layer. Theaggregated PCC and SCC(s) may have compatible control channels andtiming requirements, but may not require a separate UL channel (e.g.,for acknowledging transmissions) for the SCC(s).

In some cases, per-packet U-plane splitting performance may be optimizedto support multiple access links across RATs with different latenciesand link error rates. Similarly, per-packet U-plane splittingperformance may be optimized across licensed, shared, and/or unlicensedbands, and for cells sharing the same carrier and/or for cells onseparate carriers.

Example Protocol Stack Configurations for Aggregation and User PlaneSplitting

Different options for U-plane splitting may be described with referenceto wireless communication protocol stacks, such as the Long TermEvolution (LTE) C-plane stack 200 and U-plane stack 210 shown in FIG.2A. In the C-plane, a non-access stratum (NAS) message is received bythe radio resource control (RRC) layer and is passed down to the packetdata convergence protocol (PDCP) layer, radio link control (RLC) layerand media access control (MAC) layer. In the U-plane, an IP packet isreceived by the PDCP layer and passed down to the RLC layer and MAClayer.

As mentioned above, different levels of U-plane splitting are possible,with different corresponding considerations when making routingdecisions. For example, for a per-bearer or per IP flow split, adecision of where to serve each IP packet may be based on a Traffic FlowTemplate (TFT) associated with the bearer or IP flow. In this case, acommon PDCP layer or RLC layer may not be required between differentserving nodes as there is no reordering issue between serving nodes,since all the IP packets for a flow are routed through the same servingnode. That is, because the packets are routed based on which bearer orflow the packets belong to, all of the packets for any given flow arriveat the UE from one serving node, and the receiving UE can determine thecorrect order of the packets from indicators supplied by the node.

When packets of a flow arrive from multiple serving nodes, theindicators (e.g., sequence numbers) used by the nodes may conflict, andthe receiving UE cannot determine the proper order of the packets. Forexample, in the case of a per-bearer or per-IP-flow split, the split mayoccur at a serving gateway (SGW) via an S1 interface (e.g., for MC) orat a packet data network gateway (PGW) or home agent (HA) (e.g., forWLAN interworking), resulting in packets for the bearer or IP flow beingdelivered to multiple serving nodes which may then assign their ownindicators to the packets without coordination. For the UE to reassemblethe packets in the correct order, some coordination or additionalinformation must be provided. As an example, the node at which the splitoccurs may provide packet identifiers that determine a sequence ofpackets for the bearer, irrespective of the serving node that delivers aparticular packet. A RAN-only solution may also be possible via aninterface between serving nodes, e.g., an X2 interface.

For U-plane splitting on a per-packet basis, a common PDCP layer (forMC) across serving nodes may be utilized to reorder the packets in aflow, while RLC reordering may also be possible. In the case of U-planesplitting on a per-packet basis, the per-packet decision of where toserve each PDCP packet may be based on scheduling requirements (e.g.,bandwidth available at transmission times) on each eNB. According tocertain aspects of the present disclosure, flow control may be definedbetween the MeNB and SeNB to allow the MeNB and SeNB to make theper-packet determinations of where to serve each PDCP packet.

In certain systems (e.g., current LTE), mobility and aggregation aregenerally based on the principle that a UE is served by a single servingeNB on the C-plane, meaning that RRC and NAS signaling are only sent tothe UE via a single eNB. In some versions of these systems, a UE mayalso be served by up to 2 serving eNBs on the U-plane, and by multiple(e.g., up to 5 in Release 12 of LTE) cells across the 2 serving eNBs.

FIG. 2B illustrates an example configuration 230 of carrier aggregationfor the U-plane protocol stack for an eNB having a primary componentcarrier (PCC) f1 and secondary component carriers (SCCs) f2-f5 incurrent wireless communication systems (e.g., LTE Rel-10). In carrieraggregation (CA), reconfiguration, addition, and removal of secondarycells (SCells) within a single serving eNB may be performed by the RRCfunction. The primary cell (PCell), belonging to the same eNB, is usedfor transmission of physical uplink control channels (PUCCH), and NASinformation is taken from the PCell. Cross-carrier scheduling, via acarrier indicator field (CIF), allows the physical downlink controlchannel (PDCCH) of a serving cell (e.g., the PCell) to scheduleresources on another serving cell. Unlike SCells, it may not be possibleto remove or deactivate a PCell.

A PCell serving a UE may be changed with a handover procedure (i.e. witha security key change and RACH procedure). For handover from one LTEPCell to another LTE PCell, RRC functions can also add, remove, orreconfigure SCells for usage with the target PCell. As a result, the UEmay be able to handover (HO) to a target eNB and continue CA without there-establishing connections to SCells serving the UE. Re-establishmentof connections by the UE is triggered when the PCell serving the UEexperiences RLF, but not when SCells experience RLF. UEs operating in aCA system generally receive data faster due to the increased availablebandwidth in a CA system than in a system without CA.

FIG. 3 illustrates an example configuration 300 of a dual connectivityprotocol stack linking (via an X2 connection) an MeNB and an SeNB. Theprotocol stack for a particular bearer generally depends on how thatbearer is setup. For example, various alternative types of bearer exist:MCG bearers, split bearers, and SCG bearers. For MCG bearers (e.g., theleft bearer in FIG. 3), the MeNB is U-plane connected to the S-GW via anS1-U interface and the SeNB is not involved in the transport of userplane data for this bearer. For split bearers (e.g., the middle bearerin FIG. 3), the MeNB is U-plane connected to the S-GW via an S1-Uinterface and, in addition, the MeNB and the SeNB are interconnected viaan X2-U interface, allowing both the MeNB and the SeNB to deliverU-plane data to the UE. For SCG bearers (e.g., the right bearer in FIG.3), the SeNB is directly connected with the S-GW via an S1-U interface.

Signaling radio bearers (SRB) are typically of the MCG bearer type and,therefore, use radio resources provided by the MeNB. At least one cellin SCG typically has a configured UL RRC connection, and one of them isconfigured with PUCCH resources, which may be used for controlprocedures (e.g., data scheduling) that do not require the existence ofan SRB. As noted above, re-establishment may be triggered when the PCellexperiences RLF, but not when an SCell experiences RLF. The MeNBmaintains the radio resource management (RRM) measurement configurationof the UE and may decide to request an SeNB to provide additionalresources (serving cells) for a UE (e.g., based on received measurementreports or traffic conditions or bearer types). In this case, the MeNBand the SeNB may exchange information about UE configuration by means ofRRC containers (inter-node messages) carried in X2 messages. In DC, twocell radio network temporary identifiers (C-RNTI) are typicallyindependently allocated to a UE, one for use in communicating with theMCG, and one for use in communicating with the SCG.

Example User Plane Offload Options

As used herein, the term offload generally refers to the breaking out(i.e., offloading) of data at an earlier point in the path. For example,if data is routed from one path (e.g., through an MeNB and an SeNB) to ashorter path (e.g, through an SeNB only), then the data is said to beoffloaded. For example, a UE may be said to be operating with minimaloffload for a flow, if all data is routed through a GW in the CN via anMeNB. The UE may be said to be operating with local offload for a flow,if all data is routed through a LGW in the MeNB while the UE may be saidto be operating with maximum offload for the flow if all the data isrouted through a LGW in the SeNB and does not traverse the MeNB.

As used herein, the term User plane (U-plane) splitting generally refersto how the traffic is delivered from the GW to the UE. As will bedescribed in greater detail below, decisions regarding where to offloadtraffic and how to configure U-plane splitting may be based on the dataservice requirements and other considerations (e.g., available resourcesand radio frequency (RF) conditions of potential offload targets).

FIG. 4 illustrates various U-plane offload options. In a firstconfiguration 410, the GW 140 for U-plane data, such as operatorservices and voice over LTE (VoLTE), may be in the core network (CN). Inthe first configuration, the U-plane data may be described as minimallyoffloaded (from the perspective of the core network), because the commongateway 140 is upstream of the MeNB and SeNB.

In a second configuration 420, the GW may be at the MeNB (shown as localor logical gateway LGW) for traffic requiring “local” session continuitywithin the service area of the MeNB, such as selected internet IPtraffic offload (SIPTO) at the RAN. In the second configuration, the“local” session traffic may be described as being in a greater offload(e.g., more offloaded) than the traffic in the first configurationbecause the local gateway 422 is located at the MeNB, meaning that datahandling (e.g., routing) for such traffic can take place at the MeNBrather than at nodes in the core network.

In a third configuration 430, the LGW 432 is at the SeNB fornon-seamless traffic (e.g., SIPTO at a local network). In the thirdconfiguration, the non-seamless traffic may be described as completely(or maximally) offloaded, as the gateway is located at the SeNB, andthus none of the traffic traverses the MeNB or the network operatorgateway. Mobility for the services provided to the UE decreases as theoffload increases, because mobility (e.g., handovers) are managed by theMeNB, but the offloaded traffic is traversing and even being managed bythe SeNB.

Decisions on where and how to offload data may have significant impactson performance and implementation complexity. For example, data offloadin the RAN may reduce overall U-plane traffic at the CN and enableefficient access to local services. However, this same offload mayimpact user experience for highly mobile UEs due to the need to relocateor modify the gateway functionality if the UE changes cells, and mayalso increase backhaul connectivity requirements for data forwardingbetween cells for local session continuity.

FIG. 5 illustrates three example U-plane splitting options. U-planesplitting configurations generally define how and where bearers areserved by the network and UE for seamless connectivity. Decisionsregarding whether U-plane data is split on a per-packet basis (packetsplitting) or a per-bearer basis (bearer splitting) may be based oncoupling between the MeNB and SeNB. In addition, the decisions may be afunction of UE capability and backhaul availability

As illustrated, in a first configuration 510, U-plane data may be routedto or from the core network GW 140 via the SeNB 130. This is an exampleof bearer splitting in the core network.

A second configuration 520 shows per-bearer U-plane splitting (or simplybearer splitting) in the RAN. That is, the packets are routed based onwhich bearer each packet is for by the core network in configuration 510and by the RAN in configuration 520.

A third configuration 530 shows per-packet U-plane splitting (or simplypacket splitting) in the RAN. As illustrated, in this configuration,some packets for a bearer are served by the MeNB while other packets areserved by the SeNB.

For bearer splitting, there may be no need to route, process and bufferbearer traffic served by the SeNB at the MeNB. As a result, there is noneed to route all traffic to the MeNB, which may allow for lessstringent requirements on the backhaul link between the MeNB and theSeNB (e.g., less bandwidth demands and higher latency tolerated). Inaddition, bearer splitting may provide support of SIPTO and contentcaching at the SeNB, as well as independent protocol stacks on each linkas there is no requirement for coordinated flow control between the twolinks.

In some cases, packet splitting may have advantages over bearersplitting. For example, for bearer splitting the offloading may need tobe performed by a mobility management entity (MME) configuring thetunnels (e.g., IPSec tunnels or other protocol tunnels) at the SGW and,as a result, dynamic changes to the configuration of bearers may belimited and may require SeNB mobility to be visible to the CN. That is,if a UE moves out of the service area (e.g., a cell) of an SeNB, the CNmust be informed so that the CN can reconfigure the bearers for the UE.For bearers handled by the SeNB, handover-like interruption may occurwith SeNB changes, with data forwarding between SeNBs. Further,utilization of radio resources across an MeNB and an SeNB for the samebearer may not be possible in many cases.

Packet splitting may enable CA-like gains across cells and finegranularity load balancing (as routing decisions are made per-packetrather than per-bearer). Packet splitting may also enable more dynamicbearer switching based on cell loading and may also reduce CN signalingas SeNB mobility may be partly or entirely hidden from the CN. That is,the CN may not be informed of a UE moving out of a service area of aparticular SeNB, as the CN forwards the packets to the RAN, and the RANdetermines which SeNB (or the MeNB) delivers the packet to the UE.Further, as routing decisions are made per-packet, no data forwardingbetween SeNBs may be required upon a change of the SeNB (e.g., whenchanging SeNBs, packets may simply not be routed to an SeNB beingde-activated), thus relaxing requirements for SeNB mobility. Inaddition, utilization of radio resources across MeNB and SeNB for thesame bearer may be possible.

In some cases, bearer splitting may have advantages over packetsplitting. For example, packet splitting may require routing, processingand buffering all traffic in the MeNB and may also increase backhaulconnectivity requirements, relative to bearer splitting, for dataforwarding between cells, and packet splitting does not readily supportSIPTO or content caching at the SeNB. In addition, packet splitting mayrequire coordinated flow control and may result in more complex protocolstacks (relative to bearer splitting) to account for different links andover the air (OTA) and backhaul latencies.

Example Control Plane Options

Various RRC functions may be relevant for the SeNB operation used in MCrouting. For example, common radio resource configurations of an SeNB,dedicated radio resource configurations, and measurement and mobilitycontrol for the SeNB, may be relevant to MC routing.

FIG. 6 illustrates example control plane logical architecture optionsfor RRC. In some cases, the RRC packets for the MeNB 120 may be sent tothe MeNB via the SeNB 130 and forwarded over the backhaul (configuration620) and/or vice versa (configuration 610). In this case, the RRCmessaging (or other RAT equivalent signaling) may need to support anaddress scheme over the air (OTA) to identify the target (whether MeNBor SeNB) for the packet.

As illustrated by configuration 610, the RRC logical architecture mayinclude a single RRC instance in an MeNB, wherein any RRC messagesdelivered via an SeNB are tunneled via the MeNB RRC instance. Asillustrated by configuration 620, the RRC logical architecture may alsoinclude separate RRC (or equivalent) instances in the MeNB and the SeNB,for example, with the separate independent instances managing the airlink configuration. In this case, coordination over X2 may be needed forUE configuration, for example, the MeNB and SeNB may coordinate toassign common or mutually compatible discontinuous reception (DRX)parameters to the UE.

In some cases, the RRC functionality allowed in the SeNB may only be asubset of the full RRC functionality (e.g., if only the MeNB managesmobility of the UE in connecting to the SeNB and U-plane splittingconfiguration). In this case, the RRC instance in the MeNB may beconsidered a primary RRC and the RRC instance in the SeNB may beconsidered a secondary RRC. In some cases, the SeNB may be associatedwith a different RAT as compared to the MeNB, which may be similar tohaving separate systems as there may be no requirement for the MeNB tomanage the configuration of the SeNB air link to the UE.

FIG. 7 illustrates C-plane NAS logical architecture options. The NASlogical architecture options include a single NAS instance in an MME702, served by lower layer transport through a single MeNB 120 asillustrated by configuration 710. The protocol stack in the MeNBprovides transport for NAS messages exchanged by the UE with the MME. Inthis logical architecture, NAS messages may or may not be sent throughthe SeNB 130, depending on the RRC logical architecture used with theNAS architecture. NAS messages to be sent through the SeNB are forwardedto the SeNB from the MeNB (for delivery from the MME to the UE), orforwarded to the MeNB from the SeNB (in case of delivery from the UE tothe MME).

A second C-plane NAS logical architecture option is to include anindependent instance in each of the MeNB and the SeNB of a protocollayer capable of delivering messages to a NAS instance in the MME (e.g.,an RRC layer), as illustrated by configuration 720. In the second NASarchitecture, the MME 702 exchanges NAS messages via both the MeNB 120and the SeNB 130. In such an architecture the MME may operate a singleNAS protocol instance with the ability to coordinate separatecommunications with the SeNB and the MeNB. The protocol layerimplemented in the SeNB for communication with the NAS layer in the MMEmay comprise only a subset of the underlying protocol; e.g., an RRClayer in the SeNB may not support all functions of a complete RRCinstance, as described further below.

A particular example implementation of a C-plane NAS and RRC logicalarchitecture may have separate RRC (or equivalent) instances in an MeNBand an SeNB with a single NAS in the MeNB. The separate RRC instancesmay require some coordination over X2 for dedicated and common resourcesin order to serve the UE, although this coordination may be invisible tothe UE. As noted above, the RRC instance in the SeNB may only be asubset of a full RRC (e.g., the RRC of the MeNB may act as a primary RRCwhich manages mobility of the UE to the SeNB and U-plane splittingconfiguration, and the RRC of the SeNB may act as a secondary RRC withlimited functionality, such as having only the ability to providetransport for NAS messages without supporting the mobility and resourcemanagement functions that would normally be present in a fullyimplemented RRC protocol instance). NAS messages from the single NASinstance in the MeNB may be sent to either the MeNB or the SeNB. A newprocedure may be used to reconfigure the SeNB to function as an MeNB fora particular UE, for example, as a “failover” mechanism in the case ofRLF on the MeNB.

Example Control Plane Mobility

FIG. 8 illustrates an example call flow diagram 800 for a C-planemobility procedure, where a DC data path is shown as a dashed line forPDCP aggregation. As illustrated, the C-plane mobility procedure mayoccur in four general phases. The four phases apply for mobility duringboth handover and multi connectivity. The four phases may include a UEmobility configuration phase 802, a RAN mobility preparation phase 804,a mobility execution phase 806, and a mobility completion phase 808.

The UE mobility configuration phase 802 begins with, for example, the UEestablishing a connection and receiving, from the MeNB, a measurementconfiguration. UE mobility configuration allows the RAN to configure theUE to set the RF triggers for mobility. This includes the RF conditionson the serving cell, neighbor cells (both intra and inter RAT), andrelative conditions between the serving and neighbor cells. The UEmobility configuration includes service and context aware events. Forexample, based on a specific traffic type, the UE may performmeasurements on frequencies or other resources to trigger mobilityevents to RATs or channel resources specific to a certain type oftraffic (e.g., a type defined by latency or other QoS aspects, low powerrequirements for the UE, or a content type, e.g., Multimedia BroadcastMulticast Service (MBMS)). In certain aspects, the network may provideconfiguration, including context and service configuration, for a UE todetermine when to perform HO measurements (UE-centric measurementtriggering). In other aspects, the UE provides context and service stateto the network, and the network triggers measurement events based on thestate (network-centric measurement triggering). Both UE- andnetwork-centric measurement triggering may be in use in a single system,e.g., for different event types.

During the RAN mobility preparation phase 804, the UE context isprovided to the SeNB or a target eNB. For example, the UE sends ameasurement report to the MeNB, which makes a mobility decision based onthe measurement report. The MeNB then, for example, sends a mobilityrequest via the X2 connection to the target eNB (the prospective SeNB)to perform admission control. For backward HO, the UE context is sent tothe target eNB before the HO or DC event, for example, triggered basedon the UE measurement report in response to the mobility configuration.For forward HO, the context is sent after the HO event, i.e., sendingthe context is triggered as a pull from the target eNB in response tothe UE establishing a connection at the target eNB and identifying thesource eNB. The backward-HO approach would typically be expected formulti-connectivity mobility events, but the forward-HO approach is alsopossible, Sending the context after the HO or DC event (the forward-HOmodel) may provide a potential for more efficient preparation ofmultiple target eNBs, when compared to sending the context before the HOevent. Moreover, sending the context after the HO or DC event may allowfor differentiation between handovers within a cloud or cluster andhandovers to a BS outside the cloud or cluster. For example, for intracloud handover, coordinated multipoint (CoMP) concepts may be extendedto provide a single logical context across the cloud that does notchange when the point of attachment changes, and actual HO (e.g.,transferring the control-plane function for the UE from one eNB toanother) may only be needed for inter cloud UE mobility.

During the mobility execution phase 806, the UE may establish aconnection at the SeNB or target eNB. The newly established connectionallows UL and DL data to be communicated via the SeNB or target eNB. Forexample, the SeNB sends a mobility request acknowledgement via the X2connection to the MeNB. The MeNB then sends an RRC connectionreconfiguration message to the UE. The UE then synchronizes to the newcell, sends a random access preamble to the SeNB, and receives a randomaccess response from the SeNB. The MeNB then sends the sequence number(SN) status transfer message to the SeNB and begins data forwarding.This approach may provide the potential to perform an inter-cluster HOwhile maintaining IP connections via selected IP traffic offload (SIPTO)and local IP access (LIPA). In addition, this approach may allowoptimized procedures to assign a new IP address on HO, as well asenabling more make before break (as compared to current HO techniques)for mission critical applications, due to multi connectivity. MPTCP canbe used (e.g., end-to-end) if required, or applications can bemulti-homed or designed to handle IP address changes.

During the mobility completion phase 808, the network moves any tunnelsassociated with the SeNB or target eNB and the SGW to point directly tothe SeNB or target eNB and in the case of HO, releases resources on thesource eNB.

Example Multicasting Traffic Using Multi-Connectivity

As described above, when a UE is connected to a core network viamulti-connectivity (e.g., dual connectivity), data for a bearer may betransmitted to or from the UE via the MeNB or the SeNB.

According to certain aspects of the present disclosure, for certainmission critical services, in order to help ensure data deliveryreliability requirements (e.g., packet loss, latency requirements, orQoS requirements) are met, a UE may be configured to send the sameduplicate packet to both the MeNB and SeNB. By sending duplicate packetsto both the MeNB and the SeNB, the probability of successful and timelydelivery of the packet, to core network servers for example, may beincreased. Similarly, downlink packets for certain services may also beduplicated and sent to the UE via both the MeNB and SeNB.

According to aspects of the present disclosure, such duplicate packetsmay be sent using a new type of bearer, referred to herein as aduplicate-delivery bearer. According to aspects of the presentdisclosure, the duplicate-delivery bearer may be used to exchange databetween a core network and a UE connected via multi-connectivity (e.g.,via an MeNB and one or more SeNBs).

In some cases, when a duplicate-delivery bearer is used forcommunications, the MeNB is U-plane connected to the S-GW via an S1-Ubearer, and the MeNB and the SeNB are interconnected via an X2-Uinterface. Thus, the duplicate-delivery bearer may be similar to acombination of the MCG bearer and SCG bearer, described above withreference to FIG. 3.

FIGS. 9A and 9B illustrate examples of transmitting packets usingmulti-connectivity, according to aspects of the present disclosure. Theexamples involve exchanges of messages between a gateway (GW), an MeNB,an SeNB, and a UE. The exchange of messages may be performed accordingto current (e.g., Rel-10) techniques.

Turning to FIG. 9A, at (1), gateway 140 receives a DL packet addressedto the UE 110. At (2), the gateway sends the DL packet to the MeNB 120,which determines, based on, e.g., channel conditions or schedulingconstraints, to deliver the packet to the UE. The MeNB buffers thepacket prior to delivery to the UE. At (3), the MeNB delivers the DLpacket to the UE. At (4), the UE sends an ACK to the MeNB. At (5), theUE sends a report (e.g., a PDCP or RLC status report, or a bitmapindicating acknowledged and non-acknowledged packets) to the MeNBindicating that the UE has received the DL packet. When the MeNBreceives the report, the MeNB flushes the packet from the buffer of theMeNB. If delivery of the packet to the UE is unsuccessful, then the UEdoes not report receipt of the packet, and the MeNB may retransmit (notshown) the packet to the UE.

Turning to FIG. 9B, at (1), the gateway 140 receives a DL packetaddressed to the UE 110. At (2), the gateway sends the DL packet to theMeNB 120, which determines, based on, e.g., channel conditions orscheduling constraints, to forward the packet to the SeNB 130 fordelivery to the UE. The MeNB forwards the packet to the SeNB, and theSeNB buffers the packet prior to delivery to the UE. At (3), the SeNBdelivers the DL packet to the UE. At (4), the UE sends an ACK to theSeNB. At (5), the UE sends a report (e.g., a PDCP or RLC status report,or a bitmap indicating acknowledged and non-acknowledged packets) to theSeNB indicating that the UE has received the DL packet. When the SeNBreceives the report, the SeNB flushes the packet from the buffer of theSeNB. If delivery of the packet to the UE is unsuccessful, then the UEdoes not report receipt of the packet, and the SeNB may retransmit (notshown) the packet to the UE.

While the examples illustrated in FIGS. 9A and 9B show only a singleSeNB, the disclosure is not so limited and includes larger numbers ofSeNBs. The illustrated examples show DL packets being sent from a corenetwork entity to a UE, but the disclosure is not so limited and may besimilarly applied to UL packets being sent from a UE to a core networkentity.

FIGS. 10A, 10B, 10C, and 10D illustrate examples of transmittingduplicate packets using multi-connectivity, according to aspects of thepresent disclosure. The examples involve exchanges of messages between agateway (GW), an MeNB, an SeNB, and a UE. The exchanges of messages maybe performed using a duplicate-delivery bearer, as previously described.

Referring first to FIG. 10A, at (1), by the gateway 140 receives a DLpacket, of a data flow configured for multi-connectivity, addressed tothe UE. At (2), the gateway sends the DL packet to the MeNB 120, whichin turn sends a duplicate of the DL packet to the SeNB 130 for deliveryto the UE 110. The MeNB and the SeNB both buffer the packet prior toattempting delivery to the UE. At (3), the MeNB and the SeNB attempt todeliver the DL packet to the UE. At (4), the UE sends an ACK to the MeNBand a NAK to the SeNB.

In the example shown in FIG. 10A, the MeNB is unsuccessful in deliveringthe packet (e.g., due to interference). The MeNB and the SeNB may notcoordinate when they send the packet when they are delivering the DLpacket to the UE. This exchange of messages is different from a softhandover exchange of messages, in that each of the MeNB and the SeNBsends the packet independently (for example, each of the MeNB and SeNBmay independently schedule the packet to be sent on the PDSCH of theMeNB and SeNB respectively), while in soft handover, the source eNB andtarget eNB coordinate sending a packet in time and air link resources.In addition, each of the MeNB and the SeNB receives a separate ACK orNAK at the MAC layer, while in soft handover, a source eNB and a targeteNB both receive a single ACK or NAK sent by a UE at the MAC layer toboth the source eNB and the target eNB.

At (5), the UE determines the received packet was received via aduplicate-delivery bearer and sends a report (e.g., a PDCP or RLC statusreport, or a bitmap indicating acknowledged and non-acknowledgedpackets) to the MeNB and the SeNB indicating that the UE has receivedthe DL packet. The MeNB and the SeNB receive the report from the UE andeach flush the packet from their respective buffers. The MeNB flushesthe packet without attempting a retransmission, despite that the MeNBdid not successfully deliver the packet at 1006.

Turning to FIG. 10B, at (1), the gateway 140 receives a DL packet, of adata flow configured for multi-connectivity, addressed to the UE. At(2), the gateway sends the DL packet to the MeNB 120, which in turnsends a duplicate of the DL packet to the SeNB 130 for delivery to theUE 110. The MeNB and the SeNB both buffer the packet prior to attemptingdelivery to the UE.

At (3), the MeNB and the SeNB attempt to deliver the DL packet to theUE. In this example, the SeNB is unsuccessful in delivering the packet(e.g., due to interference). As above, the MeNB and the SeNB may notcoordinate when they send the packet when they are delivering the DLpacket to the UE. At (4), the UE sends an NAK to the MeNB and an ACK tothe SeNB. At (5), the UE determines the received packet was received viaa duplicate-delivery bearer and sends a report (e.g., a PDCP or RLCstatus report, or a bitmap indicating acknowledged and non-acknowledgedpackets) to the MeNB and the SeNB indicating that the UE has receivedthe DL packet. The MeNB and the SeNB receive the report from the UE andeach flush the packet from their respective buffers. The SeNB flushesthe packet without attempting a retransmission, despite that the SeNBdid not successfully deliver the packet at (3).

In FIG. 10C, at (1), the gateway 140 receives a DL packet, of a dataflow configured for multi-connectivity, addressed to the UE. At (2), thegateway sends the DL packet to the MeNB 120, and, as above, the MeNBsends a duplicate of the DL packet to the SeNB 130 for delivery to theUE 110. As above, the MeNB and the SeNB both buffer the packet prior toattempting delivery to the UE.

Similarly to above, at (3), the MeNB and the SeNB deliver the DL packetto the UE. As above, the MeNB and the SeNB may not coordinate when theysend the packet when they are delivering the DL packet to the UE. At(4), the UE sends an ACK to the MeNB and an ACK to the SeNB. At (5), theUE determines the received packet was received via a duplicate-deliverybearer and sends a report (e.g., a PDCP or RLC status report, or abitmap indicating acknowledged and non-acknowledged packets) to the MeNBand the SeNB indicating that the UE has received the DL packet.

The MeNB and the SeNB receive the report from the UE and each flush thepacket from their respective buffers. According to certain aspects, theMeNB and the SeNB may deliver the packet at different times, and the UEmay send a report reporting receipt of the packet in response to each ofthe deliveries at the different times.

Turning to FIG. 10D, at (1), the gateway 140 receiving a DL packet, of adata flow configured for multi-connectivity, addressed to the UE. As inFIGS. 10A, 10B, and 10C, at (2), the gateway sends the DL packet to theMeNB 120, which in turn sends a duplicate of the DL packet to the SeNB130 for delivery to the UE 110. As above, the MeNB and the SeNB bothbuffer the packet prior to attempting delivery to the UE.

At (3), the MeNB and the SeNB attempt to deliver the DL packet to theUE, but both are unsuccessful (e.g., due to interference). As above, theMeNB and the SeNB may not coordinate when they send the packet when theyare attempting delivery. At (4), the UE sends an NAK to the MeNB and aNAK to the SeNB. At (5), the MeNB and the SeNB each determine that theUE has not reported receipt of the packet, and attempt retransmission ofthe packet to the UE. If the NAK is not received, the MeNB and SeNB may,for example, start a timer at (3) and wait for the timer to expirebefore determining that retransmission should be attempted at (5).

In the examples in FIGS. 10A, 10B, 10C, and 10D, both the MeNB and SeNBattempt to deliver the DL packet to the UE. In some cases, however, oneof the eNBs may actually deliver the DL packet before the other eNB isable to attempt delivery of the DL packet (e.g., due to differenttransmission delays, different queuing delays, different backhauldelays, or different interference).

In cases where an eNB does not attempt delivery, if the other eNBsuccessfully delivers, then the communication exchange is similar tothose shown in FIGS. 10A and 10B, with the UE reporting receipt of thepacket to both the MeNB and the SeNB, and the MeNB and SeNB bothflushing the packet from their respective buffers. The MeNB and SeNB mayoperate using the example protocol stacks shown in FIG. 3. The reportsfrom the UE refer to an identifier for the packet (e.g., a packetsequence number) that refers to the duplicate packets at the common PDCPlayers shown in FIG. 3, so that the MeNB and SeNB may identify thedelivered packet as the same as a packet awaiting delivery (e.g.,buffered) on the MeNB or SeNB. In such cases, to avoid an unnecessarytransmission, an eNB that receives a report (e.g., an ACK) referring toa packet it has not yet delivered may refrain from delivering thatpacket.

While the examples illustrated in FIGS. 10A, 10B, 10C, and 10D each showonly a single SeNB, the disclosure is not so limited, and includeslarger numbers of SeNBs. As above with reference to FIGS. 9A and 9B, theexamples in FIGS. 10A, 10B, 10C, and 10D each show DL packets being sentfrom a core network entity to a UE, but the disclosure is not so limitedand may be similarly applied to UL packets being sent from a UE to acore network entity.

FIG. 11 sets forth example operations 1100 for reporting a status for adata flow in which duplicate packets are being received from more thanone connection (i.e., multi-connectivity), according to aspects of thepresent disclosure. The operations 1100 may be performed, for example,by a UE, such as the UE 110 shown in FIGS. 10A, 10B, 10C, and 10D.

The operations begin, at 1102, by the UE, for example, determining adata flow is being received from a plurality of connections. At 1104,the operations continue by the UE, for example, reporting, on more thanone connection of the plurality of connections, a status for a packetreceived on the data flow. Examples of these operations are illustratedabove with reference to FIGS. 10A, 10B, and 10C.

According to certain aspects of the present disclosure, the data flow issent according to layers in a protocol stack below a layer determinedbased on a selection of a packet split at an aggregation point. That is,an aggregation point (e.g., a gateway or eNB) may determine to splitpackets of a data flow at a layer (e.g., an RLC layer or a PDCP layer)in a protocol stack, and the data flow is sent using the layers at orbelow the determined layer. In certain aspects, the determined layercomprises a packet data convergence protocol (PDCP) layer or radio linkcontrol (RLC) layer.

According to certain aspects of the present disclosure, reporting astatus comprises sending a PDCP status report or sending an RLC statusreport. That is, a UE may report a status for a packet by sending a PDCPstatus report or an RLC status report that includes an indication forthe packet. According to certain aspects of the present disclosure, thesame status is sent on each connection of the plurality of connections.That is, a UE reports the same status (e.g., “successfully received”) oneach of the plurality of connections, even if the UE successfullyreceived the packet on some connections, but did not successfullyreceive the packet on other connections.

According to certain aspects of the present disclosure, the UE mayreceive a configuration (e.g., an RRC configuration) configuring thedata flow to be received on more than one connection. In an aspect, theconfiguration (e.g., an RRC configuration) may configure a bearer typeindicating the data flow is being sent on more than one connection. Thatis, use of a particular type of bearer (e.g., a duplicate-deliverybearer) may indicate to the UE that any data flows conveyed by that typeof bearer are being sent on more than one connection.

According to certain aspects of the present disclosure, determining adata flow is being received from a plurality of connections comprisesreceiving duplicate packets for the data flow on more than oneconnection. That is, a receiving device may determine that it hasreceived duplicate packets for a data flow and determine that the dataflow is being received from a plurality of connections.

According to certain aspects of the present disclosure, the UE may sendan indication of at least one service requirement of the data flow toanother entity (e.g., a core network entity). For example, a UE mayinform a core network entity (e.g., an MME) that a data flow requires aparticular QoS or indicate a service, and the core network entitydetermines the QoS for the indicated service. According to certainaspects of the present disclosure, the UE may send an indicationrequesting the data flow be sent on more than one connection based on atleast one service requirement of the data flow. For example, a UE maydetermine that a data flow requires a very low latency, and request thatthe data flow be sent on multiple connections, based on determining thedata flow requires a very low latency.

FIG. 12 sets forth example operations 1200 for transmitting duplicatepackets of a data flow on a plurality of connections (i.e.,multi-connectivity), according to aspects of the present disclosure. Theoperations 1200 may be performed, for example, by a base station (BS),such as the MeNB and the SeNB shown in FIGS. 10A, 10B, 10C, and 10D.

The operations begin, at 1202, by the BS, for example, determining adata flow is to be transmitted on a plurality of connections, whereinthe data flow is sent according to layers in a protocol stack below alayer determined based on a selection of a packet split at anaggregation point. That is, an aggregation point (e.g. a BS or gateway)for a data flow may determine to split packets of the data flow at alayer (e.g., an RLC layer or a PDCP layer) in a protocol stack, and thenother devices serving the data flow (e.g., a BS) determine (e.g., basedon control messages exchanged by network entities) the data flow is tobe sent on a plurality of connections (e.g., using the layers at orbelow the determined layer). At 1204, the operations continue by the BS,for example, forwarding data (e.g., data packets) for the data flow onthe plurality of connections.

According to certain aspects of the present disclosure, the determinedlayer comprises a packet data convergence protocol (PDCP) layer or aradio link control (RLC) layer. For example, a BS may determine to splita data flow at the PDCP layer and send duplicate PDCP packets for thedata flow via multiple connections.

According to certain aspects of the present disclosure, the BS mayreceive a status report indicating data which has been received. Forexample, a BS may receive a status report indicating particular packetshave been received by a UE. In an aspect, the status report may comprisea PDCP status report or an RLC status report. In another aspect, thestatus report indicates the data has been received on a first connectionof the plurality of connections, and the BS ceases forwarding the dataon other connections of the plurality of connections.

According to certain aspects of the present disclosure, the BS maytransmit a request to configure the data flow to be sent on more thanone connection. In an aspect, a request to configure the data flow to besent on more than one connection may include configuring a UE to receivethe data flow on more than one connection via, for example, RRCconfiguration. In an aspect, the configuration (e.g., an RRCconfiguration) may comprise configuring a bearer type indicating thedata flow is being sent on more than one connection. That is, use of aparticular type of bearer (e.g., a duplicate-delivery bearer) mayindicate (e.g., to a UE) that any data flows conveyed by that type ofbearer are being sent on more than one connection.

According to certain aspects of the present disclosure, the BS mayreceive a configuration for the data flow to be sent on more than oneconnection (e.g., from a core network entity). According to certainaspects of the present disclosure, the BS may determine a data flow isto be transmitted on a plurality of connections based on at least oneservice requirement of the data flow. For example, a BS may determinethat a data flow requires a very low latency, and determine to send thedata flow on multiple connections, based on determining the data flowrequires a very low latency.

FIG. 13 illustrates various components that may be utilized in amulti-connectivity enabled wireless device 1300 capable of operating inaccordance with aspects provided herein. The wireless device 1300 may,for example, be one implementation of UE 110 shown in FIG. 1.

The wireless device 1300 may include one or more processors 1304 whichcontrol operation of the wireless device 1300. The processors 1304 mayalso be referred to as central processing units (CPUs). The processors1304 may perform, or direct the UE in performing, multicasting andreporting status of data flows, as described above with reference toFIG. 11 and FIG. 12. Memory 1306, which may include both read-onlymemory (ROM) and random access memory (RAM), provides instructions anddata to the processors 1304. A portion of the memory 1306 may alsoinclude non-volatile random access memory (NVRAM). The processors 1304typically perform logical and arithmetic operations based on programinstructions stored within the memory 1306. The instructions in thememory 1306 may be executable to implement the methods described herein,for example, reporting status of data flows and multicasting, asdescribed above with reference to FIG. 11 and FIG. 12.

The wireless device 1300 may also include radios 1310 and 1312 tocommunicate via multiple RATs for multi-connectivity. Each radio may,for example, include a transmitter and receiver, and any other “RFchain” components to allow transmission and reception of data betweenthe wireless device 1300 and different RATs. While two radios are shownfor two RATs, as an example only, more than two radios may be included(e.g., to support more than two RATs). Each radio may communicate via asingle or a plurality of antennas 1316.

The wireless device 1300 may also include a signal detector 1318 thatmay be used in an effort to detect and quantify the level of signalsreceived by the transceiver 1314. The signal detector 1318 may detectsuch signals as total energy, energy per subcarrier per symbol, powerspectral density and other signals. The wireless device 1300 may alsoinclude a digital signal processor (DSP) 1320 for use in processingsignals.

FIG. 14 illustrates various components that may be utilized in a basestation 1400 capable of participating in communication with amulti-connectivity enabled wireless device. The base station 1400 may,for example, be one implementation of MeNB 120 or SeNB 130 shown in FIG.1.

The base station 1400 may include one or more processors 1404 whichcontrol operation of the base station 1400. The processors 1404 may alsobe referred to as central processing units (CPUs). The processors 1404may perform, or direct the BS in performing, multicasting and reportingstatus of data flows, as described above with reference to FIG. 11 andFIG. 12. Memory 1406, which may include both read-only memory (ROM) andrandom access memory (RAM), provides instructions and data to theprocessors 1404. A portion of the memory 1406 may also includenon-volatile random access memory (NVRAM). The processors 1404 typicallyperform logical and arithmetic operations based on program instructionsstored within the memory 1406. The instructions in the memory 1406 maybe executable to implement the methods described herein for example, forMeNBs and SeNBs serving a multi-connectivity UE, reporting status ofdata flows and multicasting, as described above with reference to FIG.11 and FIG. 12.

The base station 1400 may also include one or more radios 1410, forexample to communicate with a UE via one or more RATs. Each radio may,for example, include a transmitter and receiver, and any other “RFchain” components to allow transmission and reception of data betweenthe base station 1400 and different UEs. Each radio may communicate viaa single or a plurality of antennas 1416. The base station 1400 may alsoinclude an interface 1412 for communicating with other base stations(e.g., via an X2 backhaul connection) or a core network (e.g., via an S1connection).

The base station 1400 may also include a signal detector 1418 that maybe used in an effort to detect and quantify the level of signalsreceived by the transceiver 1414. The signal detector 1418 may detectsuch signals as total energy, energy per subcarrier per symbol, powerspectral density and other signals. The base station 1400 may alsoinclude a digital signal processor (DSP) 1420 for use in processingsignals.

It is understood that the specific order or hierarchy of steps in theprocesses disclosed above is an illustration of exemplary approaches.Based upon design preferences, it is understood that the specific orderor hierarchy of steps in the processes may be rearranged. Further, somesteps may be combined or omitted. The accompanying method claims presentelements of the various steps in a sample order, and are not meant to belimited to the specific order or hierarchy presented.

Moreover, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise or clearfrom the context, the phrase, for example, “X employs A or B” isintended to mean any of the natural inclusive permutations. That is, forexample the phrase “X employs A or B” is satisfied by any of thefollowing instances: X employs A; X employs B; or X employs both A andB. In addition, the articles “a” and “an” as used in this applicationand the appended claims should generally be construed to mean “one ormore” unless specified otherwise or clear from the context to bedirected to a singular form. A phrase referring to “at least one of” alist of items refers to any combination of those items, including singlemembers. As an example, “at least one of: a, b, or c” is intended tocover: a, b, c, a-b, a-c, b-c, and a-b-c.

The previous description is provided to enable any person skilled in theart to practice the various aspects described herein. Variousmodifications to these aspects will be readily apparent to those skilledin the art, and the generic principles defined herein may be applied toother aspects. Thus, the claims are not intended to be limited to theaspects shown herein, but is to be accorded the full scope consistentwith the language claims, wherein reference to an element in thesingular is not intended to mean “one and only one” unless specificallyso stated, but rather “one or more.” Unless specifically statedotherwise, the term “some” refers to one or more. All structural andfunctional equivalents to the elements of the various aspects describedthroughout this disclosure that are known or later come to be known tothose of ordinary skill in the art are expressly incorporated herein byreference and are intended to be encompassed by the claims. Moreover,nothing disclosed herein is intended to be dedicated to the publicregardless of whether such disclosure is explicitly recited in theclaims. No claim element is to be construed as a means plus functionunless the element is expressly recited using the phrase “means for.”

What is claimed is:
 1. A method of reporting a status for a data flow,comprising: determining a data flow is being received from a pluralityof connections; and reporting, on more than one connection of theplurality of connections, a status for a packet received on the dataflow.
 2. The method of claim 1, wherein the data flow is sent accordingto layers in a protocol stack below a layer determined based on aselection of a packet split at an aggregation point.
 3. The method ofclaim 1, wherein reporting a status comprises sending a packet dataconvergence protocol (PDCP) status report or sending a radio linkcontrol (RLC) status report.
 4. The method of claim 1, wherein a samestatus is sent on each connection of the plurality of connections. 5.The method of claim 1, wherein determining the data flow is beingreceived from the plurality of connections comprises receiving aconfiguration indicating the data flow is being sent on more than oneconnection.
 6. The method of claim 5, wherein the received configurationcomprises a bearer type indicating the data flow is being sent on morethan one connection.
 7. The method of claim 1, wherein determining adata flow is being received from a plurality of connections comprisesreceiving duplicate packets for the data flow on more than oneconnection.
 8. The method of claim 1, further comprising sending anindication requesting the data flow be sent on more than one connectionbased on at least one service requirement of the data flow.
 9. A methodof transmitting a data flow, comprising: determining a data flow is tobe transmitted on a plurality of connections, wherein the data flow issent according to layers in a protocol stack below a layer determinedbased on a selection of a packet split at an aggregation point; andforwarding at least one data packet for the data flow on two or moreconnections of the plurality of connections.
 10. The method of claim 9,wherein the determined layer comprises a packet data convergenceprotocol (PDCP) layer or a radio link control (RLC) layer.
 11. Themethod of claim 9, further comprising receiving a status reportindicating data which has been received.
 12. The method of claim 11,wherein the status report indicates one or more data packets have beenreceived on a first connection of the plurality of connections, and themethod further comprises ceasing forwarding the one or more data packetson other connections of the plurality of connections.
 13. The method ofclaim 9, further comprising transmitting a request to configure the dataflow to be sent on more than one connection.
 14. The method of claim 9,wherein the determining comprises receiving a configuration for the dataflow to be sent on more than one connection.
 15. The method of claim 9,wherein the determining is based on at least one service requirement ofthe data flow.
 16. An apparatus for reporting a status for a data flow,comprising: means for determining a data flow is being received from aplurality of connections; and means for reporting, on more than oneconnection of the plurality of connections, a status for a packetreceived on the data flow.
 17. The apparatus of claim 16, wherein thedata flow is sent according to layers in a protocol stack below a layerdetermined based on a selection of a packet split at an aggregationpoint.
 18. The apparatus of claim 16, wherein the means for reporting astatus comprises means for sending a PDCP status report or sending anRLC status report.
 19. The apparatus of claim 16, wherein the means forreporting a status comprises means for sending a same status on eachconnection of the plurality of connections.
 20. The apparatus of claim16, wherein the means for determining the data flow is being receivedfrom the plurality of connections comprises means for receiving aconfiguration indicating the data flow is being sent on more than oneconnection.
 21. The apparatus of claim 20, wherein the receivedconfiguration comprises a bearer type indicating the data flow is beingsent on more than one connection.
 22. The apparatus of claim 16, whereinthe means for determining the data flow is being received from theplurality of connections comprises means for receiving duplicate packetsfor the data flow on more than one connection.
 23. The apparatus ofclaim 16, further comprising means for sending an indication requestingthe data flow be sent on more than one connection based on at least oneservice requirement of the data flow.
 24. An apparatus for transmittinga data flow, comprising: means for determining a data flow is to betransmitted on a plurality of connections, wherein the data flow is sentaccording to layers in a protocol stack below a layer determined basedon a selection of a packet split at an aggregation point; and means forforwarding at least one data packet for the data flow on two or moreconnections of the plurality of connections.
 25. The apparatus of claim24, wherein the determined layer comprises a packet data convergenceprotocol (PDCP) layer or a radio link control (RLC) layer.
 26. Theapparatus of claim 24, further comprising means for receiving a statusreport indicating data which has been received.
 27. The apparatus ofclaim 26, wherein the status report indicates one or more data packetshave been received on a first connection of the plurality ofconnections, and the apparatus further comprises: means for ceasingforwarding the one or more data packets on other connections of theplurality of connections.
 28. The apparatus of claim 24, furthercomprising: means for transmitting a request to configure the data flowto be sent on more than one connection.
 29. The apparatus of claim 24,wherein the means for determining the data flow is to be transmitted onthe plurality of connections comprises means for receiving aconfiguration for the data flow to be sent on more than one connection.30. The apparatus of claim 24, wherein the means for determining thedata flow is to be transmitted on the plurality of connections comprisesmeans for determining the data flow is to be transmitted on theplurality of connections based on at least one service requirement ofthe data flow.